GPS: U-Blox

Support of all available GNSS (GPS/QZSS, Galileo, GLONASS, BeiDou) and SBAS systems

Installation

U-blox Selection Guide

U-Blox GPS Receivers generally will work in Windows with OpenCPN. They require a Virtual Com Port (VCP) driver.

Installing a USB U-Blox GPS Receiver (7 or 8) is not difficult on Windows. Download and install the (latest) Gnss sensor driver here

Insert the GPS unit and open Windows Device Manager to check under Sensor whether “U-Blox GNSS Location Sensor” is present and note the value of the u-blox (virtual) COM port under Ports.

Note that there are two drivers to be installed, one for a 'sensor' and one for a 'virtual com port'. In Device Manager you should see these as shown below:

U-Blox Options Connection

Also, the Ublox devices we have experienced, run at 9600 instead of 4800 bps. This setting is important when adding the connection in OpenCPN.

The U-center App is great for checking your GPS performance. However remember to Close this application when trying to connect to the GPS Sensor with OpenCPN. The Com Port only supports one device at a time. IE: While you are running this App you will not find the GPS sensor in Opencpn.

On my Navilock 8002U GPS, I receive the GPS, SBAS, Glonass and Galileo sats. see also Increasing the number of GPS channels reported

U-Blox Sat Signal

Who are Stratux and U-Blox?

We have received many Stratux / U-Blox questions about installation, so I have tried to understand why.

  1. These GPS receivers are inexpensive.
  2. The company has an opensource DIY, Github, raspberry_pi focus.
  3. Stratux seems to provide low cost kits for Automatic Dependent Surveillance-Broadcast (ADS-B) for tracking air traffic (which can include GPS and AHRS) and weather.
  4. There seem to be two separate companies
    1. Stratux Free software https://github.com/cyoung/stratux which enables DIY and low cost ADS-B receivers for pilots. The only full-featured receivers that are compatible with every major EFB.
    2. U-Blox Builds GPS receivers, for windows and rpi and many other devices.

One user advises there is a new issue with u-blox-usb drivers:

Another Windows user has found that if the GPS data is messed up due to a driver problem, remove and reinstall the windows driver:

  1. Unplug the gps puck with OpenCpn closed.
  2. In device manager remove both the ublox virtual com-port and the ublox location sensor. Answer 'yes´to the questions if the drivers should be removed.
  3. Uninstall ucenter
  4. Restart the PC (not sure if that is needed)
  5. Plug in the gps puck again
  6. Windows 10 discovers what is going on, thinks a short while and installs a new com-port.
  7. It is shown in device manager as “Serial usb unit (com5)”. Only Windows driver (usbser.sys) is used, nothing from ublox.
  8. Start OpenCPN and connect the new com-port. Everything work fine!